This pull request standardizes the API response format for work item group counts by always using the key count (instead of sometimes using total_count) in both flat and nested groupings. This change ensures consistency in the response structure and updates related documentation, type definitions, and print statements accordingly.

API response and model consistency:

• The WorkItemGroupCountEntry model now always uses the count field for group counts, removing the previously used total_count field. This applies to both flat (single group) and nested (group + sub-group) responses.
• The API documentation and docstrings in plane/api/work_items/base.py and plane/models/work_items.py have been updated to reflect the consistent use of count in all cases. [1] [2]
• Example API responses and code comments now consistently show count instead of total_count for both top-level and nested group counts.
• Print statements in count_workspace now reference entry.count instead of entry.total_count to match the updated model.

Summary by CodeRabbit

Release Notes

• Bug Fixes

  • Corrected the response structure for grouped work item counts. Count values in sub-grouped entries are now consistently structured.

• Documentation

  • Updated API documentation to reflect the current grouped count response format and field structure.